Method and apparatus for persistent connections to a device through the use of multiple physical network connections and connection hand-offs between multiple bands, modes and networks

ABSTRACT

A method and system to provide multiple connections to a device from separate physical networks through the same logical network layer while keeping connections persistent. In order to keep connections persistent and change physical networks, at least one additional connection is needed to seamlessly accomplish the “hand-off”. If one or more signals from the network host to the device ( 35 ) are weak or degraded, then multiple connections can provide redundancy of data being sent from the host to the device reducing the amount of lost data. Multiple connections can be used to increase the amount of data that can be sent to the device at any given time. The system also contains various multiplex servers ( 49 - 42 ) that are assigned to one or more mobile devices, and acting as the device&#39;s proxy in order to transfer data back and forth.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to International Patent Application No.PCT/US03/13443, filed Apr. 29, 2003, which claims the benefit ofProvisional U.S. Patent Application No. 60/377,631, filed May 3, 2002,each of which is hereby incorporated by reference in its entirety.

BACKGROUND OF THE INVENTION

Today there exist thousands of data and voice networks that utilize manydifferent communications protocols and technologies. The most basiclevel of a network is the infrastructure, the physical equipment thatutilizes power to send and receive electromagnetic, acoustic, or opticalsignals. The base communications protocol is a specific language thatenables the sending and receiving devices to talk to each other.Additional protocols can be stacked on top of the base protocol tocreate other languages that can be transported by the physical devices.This higher-level language allows for communications over differenttypes of infrastructures and signals.

A continuing trend is to enable communication between independentnetworks. This allows devices that could previously only communicate todevices on their respective network to communicate with devices on othernetworks. An example is the public Internet, a super network comprisedof a collection of networks utilizing many different infrastructuretechnologies transmitting many types of signals utilizing many types ofbase communications protocols. The uniting element is the IP transportlayer protocol, a common language known by each device.

Some devices are fixed and have one connection to a host network that inturn has a communications gateway for communications to other networks,such as the Internet. An example of this is the personal computer (PC)or telephone. There is typically no need for these devices to havemultiple host network connections.

However, other types of devices are portable, such as mobile phones,personal digital assistants (PDA), and laptop computers. These portabledevices typically need to have support for multiple network connections.A laptop computer often incorporates a modem to connect to a hostnetwork through a phone line when the laptop is at home and an Ethernetport to connect to the host network when the laptop is at the office.The laptop may also have an IEEE 802.11 (also known as “WiFi”) PCMCIAcard that connects to the host network of a coffee shop or otherestablishment. Rarely is the laptop connected to a network or evenpowered up while in transit between destinations.

The mobile phone is connected to its host network nearly at all timesthe phone is activated. This connection is a much more complicatedprocess. The connection is established from the cell base station to thehandset via over-the-air electromagnetic signals using a variety ofcommunications protocols, such as DIMA, CDMA, GSM/GPRS, and the like.When the handset loses signal strength from one cell base station, itpicks up a signal from one or more geographically closer cell basestations that have a stronger signal. The handset establishes a hostnetwork connection with one of the closer cell base stations and thenterminates the original cell base station connection, thus keeping thehandset persistently connected to the network. This is called aconnection “handoff” and is done today on mobile networks.

In the prior art, the handoff process can only be done within acarrier's physical network. For example, a Samsung phone communicatingwith the Sprint PCS network through a CDMA cell base station on the 2.3GHz frequency would not be able to migrate to another disparate network,such as a GSM network operated by VoiceStream.

As voice and data networks come together, there becomes a greater needfor persistent connections for mobile devices across multiple frequencybands, communications protocols, and host networks. This is due to theincreased processing power of a handheld device and the advancedservices that can now be offered to a mobile user.

Both wireless consumers and wireless carriers would benefit from theability to maintain persistent connections no matter where the consumermay be. Some of the advantages are improved connection quality, expandedcoverage, lowered costs, provision of premium data services, reducedcapital expenditures, and improved speed to market.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a protocol layering diagram of the protocol stack used in themobile device.

FIG. 2 is a protocol layering diagram of the protocol stack used in thevarious servers at a network operations center (NOC).

FIG. 3 is a diagram representing a method of dividing up the varioussoftware components in the mobile device information modules.

FIG. 4 shows the physical network layout that could be used in the NOC.

FIG. 5 is a protocol diagram showing the steps involved in connectionestablishment.

FIG. 6 is a protocol diagram showing the steps involved in connectionteardown.

FIG. 7 is a protocol diagram showing the movement of data whileredundant multiplexing is in operation.

FIG. 8 is a protocol diagram showing the movement of data while switchedmultiplexing is in operation.

FIG. 9 is a protocol diagram which shows a connection handoff from onephysical connection to another caused by fading signal strength.

DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODIMENTS

A method and apparatus for maintaining a persistent connection to atleast one network, such that said persistent connection can transcendvarious network protocols and infrastructures, is described in detailherein. In the following description, numerous specific details areprovided, such as specific wireless and wireline protocols, specifictypes of devices (laptops, cell phones, PDA's), to provide a thoroughunderstanding of, and enabling description for, embodiments of theinvention. One skilled in the relevant art, however, will recognize thatthe invention can be practiced without one or more of the specificdetails, or with protocols or devices, methods, etc. In other instances,well-known structures or operations are not shown, or are not describedin detail, to avoid obscuring aspects of the invention.

The description below describes a method and system to merge separatephysical networks consisting of multiple frequency bands, communicationsprotocols, and hosts by creating a logical network layer that is capableof keeping a persistent connection with a stationary or in motiondevice.

The description below describes a method and system to provide multipleconnections to a device from separate physical networks through the samelogical network layer that keeps connections persistent. In order tokeep connections persistent and change physical networks, at least oneadditional connection is needed to seamlessly accomplish the “hand-off”.Multiple connections can increase the overall signal strength to thedevice. If one or more signals from the network host to the device areweak or degraded, then multiple connections can provide redundancy ofdata being sent from the host to the device reducing the amount of lostdata. Multiple connections can be used to increase the amount of datathat can be sent to the device at any given time. This is desirablebecause it improves the efficiency of frequency usage by allocating itin an on demand manner. Also, data delivery rates can increase, whichimproves the services the device can support. Furthermore, it isdesirable to increase the rate data is transmitted to the device withoutreplacing existing physical infrastructure or licensing new spectrum.

The description below describes a method and system that provides thislogical network layer in a way that requires no modifications in theunderlying hardware or software required by the physical network host orthe device. This approach is taken to provide backward and forwardcompatibility for physical infrastructure, communications protocols andsignal type. It does not preclude the embedding of the present inventioninto future versions of software or hardware in the areas stated above.On the contrary, it is expected that the inclusion of the presentinvention will decrease the size and complexity of future productversions. This network neutral approach is possible through the additionof client software on the client device and the use of server softwareat a network operation center (NOC). Thus, no special alterations of thephysical network is needed to deploy the present invention.

The description below describes a method and system that makes use ofboth voice and data physical networks to keep multiple persistentconnections in such a way that the logical network layer can deliverboth voice and data communications through any connection regardless ofthe primary intent of the physical network. This is accomplished byproviding a digital-based or packet-based logical network layer on topof the physical network. This allows for non-digital communicationsprotocols to carry digital protocols. In addition, voice communicationis digitally represented at the logical network layer regardless of howthe voice communication was initiated. This process is commonly referredto as VOIP.

The description below describes a method and system that merges separatephysical networks through persistent multiple connections in a way thatdoes not interfere with, or require a change in the way, the physicalnetwork identifies the device for either data or voice connectionestablishments or communication transmissions. The present inventionaccommodates this through the use of device ID, phone number, and deviceassigned IP “transparency”, “Transparency” in this case means that thephysical networks identify the device in the same manner they docurrently. This is typically done through the assignment of a phonenumber or IP to the ID of the device or to the SIM card accompanying thedevice. Usually this is done during the process of activation orregistration, but could also be done at the time the device connects tothe host physical network during authentication.

The present invention passes this identification information to theappropriate physical network for each connection. However,“transparency” also means that the logical network layer masks thisinformation from any portion of the device above the logical layerprotocol stack. Similarly, the NOC outside of the present invention'smultiplex and connection servers only identifies the device by the IDassigned by the logical network layer. Additionally the physical networkis only aware of the connection that it has with the device. Thus,connections from other physical networks to the device are transparentfrom each other. When connection requests are made to the device fromother devices, the logical ID is used, which would typically be apublished phone number or IP.

The description below describes a method and system for providing apersistent connection utilizing multiple physical network connections toa single device. The system is created through client and serversoftware that creates a logical network layer that controls thecommunications to the device. This includes controlling both voice anddata connections and transmissions and controlling the establishment and“hand-offs” of physical connections. The system provides for themonitoring of aggregate signal strength to the device and controllingthe data transmission by optimizing for weak signal redundancy ormultiplexing connections to increase bandwidth. Additionally the systemcreates connection “transparency” for both the physical networks andexternal devices. This is accomplished through a logical\physicalnetwork ID table and routing provided by the server multiplex andconnection software.

Unless described otherwise below, the construction and operation of thevarious blocks shown in the Figures are of conventional design. As aresult, such blocks need not be described in further detail herein,because they will be understood by those skilled in the relevant art.Such further detail is omitted for brevity and so as not to obscure thedetailed description of the invention. Any modifications necessary tothe blocks in the Figures (or other embodiments) can be readily made byone skilled in the relevant art based on the detailed descriptionprovided herein.

Further, where protocol layers and stacks are shown in the Figures, thistype of description is known in the art, and can itself include variousdetails that need not be described herein. Those skilled in the relevantart can create source code, microcode, program logic arrays or otherwiseimplement the invention based on the Figures and the detaileddescription provided herein. Further, while many of the embodiments areshown and described as being implemented in software, such embodimentscould equally be implemented in hardware and be performed by one or moreprocessors.

Further, the Figures and the associated discussion provide a generaldescription of a suitable environment in which aspects of the inventioncan be implemented. Although not required, embodiments of the inventionwill be described in the general context of computer-executableinstructions running on various devices. Those skilled in the relevantart will appreciate that aspects of the invention can be practiced withother computer system configurations, including Internet appliances,hand-held devices, wearable computers, cellular or mobile phones,multi-processor systems, microprocessor-based or programmable consumerelectronics, set-top boxes, network PCs, mini-computers, mainframecomputers and the like. Aspects of the invention can be embodied in aspecial purpose computer or data processor that is specificallyprogrammed, configured or constructed to perform one or more of thecomputer-executable instructions explained in detail below.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense as opposed to anexclusive or exhaustive sense; that is to say, in a sense of “including,but not limited to” Words using the singular or plural number alsoinclude the plural or singular number respectively. Additionally, thewords “herein,” “above,” “below” and words of similar import, when usedin this application, shall refer to this application as a whole and notto any particular portions of this application. When the claims use theword “or” in reference to a list of two or more items, that word coversall of the following interpretations of the word: any of the items inthe list, all of the items in the list and any combination of the itemsin the list.

Overview of Protocols

To facilitate logical transparency to the user, and physical networkindependence, the transport layer (referred to as “CoCo”) of the presentinvention uses a number of protocols, some standard and some developedspecifically for the purpose of the invention. In FIGS. 1 and 2 theseprotocols and their interrelations are shown. FIG. 4 shows thearchitecture of a network and mobile device 35 implementing the presentinvention. The logical transparency exists between layers 3 through 17.Therefore, IP traffic originating on either the network side or themobile device side is transported to and from the underlying network tothe other unmodified. In fact, the multiplex server (49-52) acts as aproxy on behalf of the mobile device.

The IP traffic is encoded and tagged with addressing information duringthe passage to the CoCo multiplex layers 4 and 18. This information isused by the intermediary machines such as the border servers 45-47.Information between the border servers 45-47 and the mobile device 35 isfurther encoded using an encapsulation mechanism 7 and 15 specific tothe underlying protocol (in this example CDMA), and then transportedusing that underlying protocol 8 and 16. Once arrived on the borderserver 45-47, parts of the multiplex subset 48 communicate using CoComultiplex over UDP (13, 19, 23).

The CoCo multiplex protocol is also used to allow the transportmanagement module (28) and the transport management server (52) tocommunicate via layering another protocol, the transport managementprotocol (9, 21) on top of CoCo multiplex protocol (4, 22).

Overview of Software Components in Mobile Device

FIG. 3 details a method of componentizing the software within the mobiledevice 35. The interface 25 is the means by which other portions of thesoftware on the mobile device 35 communicate over the CoCo transportlayer. The TCP/IP stack 26 is a normal TCP/IP stack similar to thenetwork software component of any network operating system. Thetransport management modules (TMM 28), through the interface 25, isinstructed to modify the connection (for example, bringing the entirevirtual connection (not a component physical connect) up and down, orchanging the tuning parameters used to decide what physical networks touse). The TMM 28 also receives information about the connection statefrom the various connection modules, of which three examples are givenWiFi 29, CDMA 30, and GSM 31. The TMM 28 also communicates with themultiplex module (MM 27) to change the TMM's 28 settings.

The MM 27 is in charge of actual data transport for the TCP/IP stack 26to the connection modules 29, 30, 31. The manner of subdividing thetransport among the modules will be discussed in more detail below. Thevarious connection modules 29, 30, 31 are in charge of performingencoding/decoding for their respective encapsulation layers 5, 7, 10 andpassing the results to their respective drivers 32, 33, 34 whichcommunicate to the lower level protocol layers 6, 8, 11, and eventuallyhardware.

Overview of the Network Operations Center Transport Subsystem

The NOC is the point of aggregation of all the various data paths usedby the mobile device 35, and the external address location of themobile. As is shown in FIG. 4, the mobile device 35 communicates viamultiple technologies along various paths (such as 35->36->39->42->45 or35->37->40->43->46), all of which terminate at a border server 45-47.This entire communication takes place using network addressing andprotocols known to the hardware doing the transport (for example CDMAfor CDMA networks), and does not require any of the intermediarycomponents (along the paths above) to understand any of the CoCoprotocols or make any special provisions.

Once arriving at a border server 45, 46, 47, the data is deencapsulatedvia the border server using it's understanding of the underlyingtechnology (for example, 15, and 16 for CDMA). That is, each borderserver understands only how to deal with a specific technology inrelation to encapsulation and transport. Once the deencapsulation isdone, the border server should have a CoCo multiplex 12 protocolmessage, which is either an encapsulated IP datagram 3 or a transportmanagement protocol datagram 9. This is delivered to the appropriateplace via encoding the CoCo multiplex protocol message in UDP 13 andsending it to the correct destination over the multiplex subnet 48.

There are various multiplex servers 49-52 each of which is assigned toone or more mobile devices, and acts as the device's proxy in relationto data transfer. There is also a transport management server (TMS) 52which manages connection state information for all mobile devices. ThisTMS 52 can be addressed via any machine on the internal subnet 53. Also,any machine on the internal subnet 53 can communicate to a given mobiledevice as though it were local by simply addressing the mobile device'sproxy multiplex server (such as multiplex server 50). If it is desiredto make the mobile device 35 addressable from an external network (theInternet for example), routing can be set up to allow the multiplexserver 50, to be made available to the external network though a gateway(part of 54) which is on the internal network 53.

One should note that the border servers 45-47 are all multi-homed onboth the multiplex subnet 48 and a network specific to their ownencapsulation method (42, 43, and 44 respectively). The multiplexservers (45, 46, 47) and the TMS 52 are similarly multi-homed, butbetween the multiplex subset 48 and an internal subnet 53. There is nota requirement that there be a single internal subnet; rather, differentmultiplex servers could be on different internal subnets. Also, the TMS52 does not have to be on the same internal subnet as the multiplexservers. In fact, if the internal subnet containing the multiplexservers is made externally addressable it would be advantageous from asecurity perspective for the TMS to go to its own subnet.

Connection Establishment/Teardown

The term “connection” refers to a given data path between the mobiledevice and the NOC, that is a specific set of hardware, protocols andaddressing which can be used to move data from the mobile to the NOC.Further, the connection can refer to the communication of voice or dataor both over the network. The virtual connection idea seen by the higherlayers is a purely software construct whose state depends on theunderlying connections. In this section, when the term “connections” isused, this refers to the underlying, physical connections, not thetransparent virtual one.

The decision to bring a given connection up or down is made by thetransport management module 28, and the transport management server 52.Usually, the decisions will be made via the mobile device 35, butsupport exists for any form of negotiation or control between the twotransport managers. The overall goal of the transport managementprotocol (21, 9) is to convey information between the two transportmanagers, so that they are both aware of the same current connectionstatus. However, there are times when they must independently modifytheir own state, such as an unexpected connection close.

The transport managers use information from the user (other modules 25for TMM 28, or other subsystems 54 for TMS), from the connection(connection modules 29-31 for the TMM 28, or border servers 45-47 forthe TMS 54), and from the other transport manager to make decisions onconnection changes.

The process of establishing a new connection over another physicaltransport mechanism is shown in FIG. 5. In FIG. 5, the mobile device 35has decided to initiate the connection. Should the NOC have decided toinitiate the connection, the diagram would look similar, with the TMM 55switched with the TMS 60, the MM 56 switched with the MS 59, and the CM57 switched with the base station 58.

The communications in the diagram represent asynchronous function callsbetween the modules, CoCo multiplex over UDP between the various NOCServers, and a particular encapsulation methods between the connectionmodule 57 and the border server 58.

Walking through of FIG. 5:

61. The TMM 55 decides to initiate a new connection using method X.

62. It alerts the correct connection module.

63. Which opens the physical connection.

64. Which the connection modules notes.

65. And alerts the TMM.

67. Which changes it's state and modifies the MM's settings as desired.

Meanwhile, on the other side of the connections

63. The Border Server receives the connections, causing it to

66. Alert the TMS of the new connections

68. Which then changes it's state and modifies the MM's settings asdesired.

FIG. 6 shows the similar process of connection teardown. Again, theprocess is shown based on the mobile device causing the teardown. Bymaking the same replacements described in the establishment section, thediagram would show the NOC causing the teardown. In the case of aspontaneous connection break, the connection module 71 and the borderserver 72 both alert the TMM 69 or the TMS 74 respectively via an ‘AlertClosed’ signal 79, which causes both sides to perform a ‘Remove Con’action 80, resulting in a disconnected state.

Walking though the Normal Case:

75. A close is initiated

76. The TMM removes the connection from the MM's 70 list, resulting inno further data being sent over the connection, as well as

77. Telling the correct CM 71 to close the module

78. Which it does

79. Resulting in the BS 72 noticing the close and alerting the TMS 74

80. Which calls ‘Remove Con’ 80 on the MS 73, resulting in no more databeing sent over the connection in the reverse direction

Overview of Multiplexing (Redundancy and Switching)

Mutliplexing refers to using more than one physical/logical network totransport data for a single higher level logical connection (the virtualconnection). Two types of multiplexing are supported: Redundant andSwitched. Redundant multiplexing involves sending the same data overmore than one path, thus improving the chances for correct reception.Switched multiplexing involve splitting the data over multipleconnections to improve throughput.

The CoCo model supports both, including both simultaneously. Forexample, assume there are three physical connections, A, B, and C. Onecould always send data over C, as well as either A or B, switchingbetween them. One could also use switched or redundant multiplexingacross three or more parts. The two simplest cases (two connectionswitched multiplexing and two connection redundant multiplexing) areexamined in FIGS. 7 and 8, as detailed below.

Data Transport in Two Connection Redundant Multiplexing

In FIG. 7, we see data moving from the mobile to the NOC. The reverseprocess (moving data from NOC to mobile) is identical with the changesdiscussed in the connection section.

We begin with a packet entering at 89. The multiplex module 82 thensends the packet to both of the Connection Modules 83 and 84 as seen in(90,92). Once at each module, the data is encapsulated and sent 91 and94 to the respective border server at 85 and 86. One their the data isdeencapsulated and sent (93,95) to the multiplex server 87. Uponreceiving the first packet 93 the multiplex server send the data overthe internal network 96 to it's final destination. The second packet 95is dropped. If however the first packet had been unable to make it, thesecond packet would have resulted in data still making it across.

Data Transport in Two Connection Switched Multiplexing

In FIG. 7, we see data moving from the mobile to the NOC. The reverseprocess (moving data from NOC to mobile) is identical with the changesdiscussed in the connection section.

We begin with packets 1 (105) arriving from the IP stack. Once in the MM98 one of the two connections modules is chosen based on current trafficconditions/cost/bandwidth/etc. In this case, CM A 99. The data is thensent at 106 to CM A (99) where it is encapsulated and send (107) to BS A(101) where it is deencapsulated and sent 108 to MS 103 which thenforwards the data portion over the internal network to it's finaldestination 104.

Packet 2 arrives (110) and another CM is chosen, B in this case (100),the packet travels (111,112,113) to the same MS (103) at the NOC, and issend in the same manor as the proceeding packet 1 to (104).

Use of Connection Redundancy During Handoff

FIG. 9 puts all the parts together and gives an example of a transparentconnection handoff. We start out with normal data transfer over a singleconnection (123). The process really gets started when the connectionmodule being used to deliver the data (Connection Module A, 117) noticesa weakening signal strength and alerts (124) the TMM (115). At thispoint the TMM(115) begins a connection establishment over path B (125),using the methods diagramed in FIG. 5. Once this connection isestablished, the data flows using redundant multiplexing (126) asdetailed in FIG. 7. Upon fully losing signal (127), the connection overA is torn down, which being a connection caused teardown is amodification of FIG. 6 as discussed in the section on connectionteardown. This changes the MM (116) to now use the single connection Bfor it's data transfer, thus completing the handoff

The above detailed descriptions of embodiments of the invention are notintended to be exhaustive or to limit the invention to the precise formdisclosed above. While specific embodiments of, and examples for, theinvention are described above for illustrative purposes, variousequivalent modifications are possible within the scope of the invention,as those skilled in the relevant art will recognize. For example, whilesteps are presented in a given order, alternative embodiments mayperform routines having steps in a different order. The teachings of theinvention provided herein can be applied to other systems. These andother changes can be made to the invention in light of the detaileddescription.

The elements and acts of the various embodiments described above can becombined to provide further embodiments. Aspects of the invention can bemodified, if necessary, to employ the systems, functions and concepts ofthe various patents and applications described above to provide yetfurther embodiments of the invention.

These and other changes can be made to the invention in light of theabove detailed description. In general, the terms used in the followingclaims, should not be construed to limit the invention to the specificembodiments disclosed in the specification, unless the above detaileddescription explicitly defines such terms. Accordingly, the actual scopeof the invention encompasses the disclosed embodiments and allequivalent ways of practicing or implementing the invention under theclaims.

1. A method for communicating between an originating computing deviceand a destination computing device comprising: maintaining a firstconnection between said originating device and a network operationscenter using a first network operating using a first protocol;maintaining a second connection between said network operations centerand said destination device using a second network operating under asecond protocol; communicating data to said destination device betweensaid originating device and said network operations center using saidfirst protocol via said first network; translating, at said networkoperations center, said data between said first protocol and said secondprotocol; communicating said data between said network operations centerand said destination device in said second protocol using said secondnetwork operating under said second protocol; maintaining a thirdconnection between said originating device and said network operationscenter using a third network operating under a third protocol; and whensaid first connection fails, communicating said data to between saiddestination device using said third protocol via said third network;wherein said first connection fails when a capacity of said connectiondecrease below a threshold, and wherein a capacity of said data oversaid failed first connection is above the threshold.
 2. The method ofclaim 1 wherein said first network is a voice network and said secondnetwork is a data network.
 3. The method of claim 1 wherein said firstprotocol is the 802.11 protocol and said second protocol is a cellularprotocol.
 4. The method of claim 1 wherein said connection with saidfirst network is terminated once said connection with said secondnetwork has been established.
 5. The method of claim 1, furthercomprising: translating, at said network operations center, said databetween said third protocol and said second protocol.
 6. The method ofclaim 1 wherein said first protocol, said second protocol and said thirdprotocol are different from each other.
 7. The method of claim 1 whereinsaid data comprises a first portion and a second portion, wherein saidfirst connection communicates said first portion of said data, andwherein said third connection communicates said second portion of saiddata, and wherein said second connection continues to communicate saiddata.
 8. The method of claim 1 wherein said data comprises a firstportion and a second portion, wherein said first connection communicatessaid first portion of said data, and wherein said third connectioncommunicates said second portion of said data, and wherein said secondconnection continues to communicate said data.
 9. The method of claim 1wherein said first connection fails when a physical component of saidfirst network fails.
 10. The method of claim 9 wherein said thirdconnection communicates said data, and wherein said second connectioncontinues to communicate said data.
 11. The method of claim 1, whereinsaid translating translates by de-encapsulating said data communicatedvia said first protocol, and re-encapsulating said data such that saiddata is communicable by said second protocol.
 12. The method of claim 1,wherein said data is encapsulated at said originating device beforecommunicating said data.
 13. The method of claim 12, wherein saidencapsulated data is communicable by the first protocol and the thirdprotocol.
 14. A computer-readable storage medium storing instructionsfor executing a method for communicating between an originatingcomputing device and a destination computing device comprising:maintaining a first connection between said originating device and anetwork operations center using a first network operating using a firstprotocol; maintaining a second connection between said networkoperations center and said destination device using a second networkoperating under a second protocol; communicating data to said networkoperations center using said first protocol via said first network;translating said data to a second protocol, said translating performedat said network operations center; communicating said translated datafrom said network operations center to said destination device in saidsecond protocol using said second network operating under said secondprotocol; maintaining a third connection between said originating deviceand said network operations center using a third network operating undera third protocol; and when said first connection fails, communicatingsaid data to said destination device using said third protocol via saidthird network; wherein said first connection fails when a capacity ofsaid first connection decreases below a threshold, and wherein acapacity of said data over said failed first connection is above thethreshold.
 15. A computing system for communicating between anoriginating computing device and a destination device comprising: aprocessor; and a memory communicatively coupled to said processor,wherein said processor controls a first component that maintains a firstconnection between said originating device and a first border server ata network operations center using a first network operating under afirst protocol, wherein said processor controls a second component thatmaintains a second connection between said first border server and saiddestination device using a second network operating under a secondprotocol; wherein said processor controls a third component thatcommunicates data between said destination device and said first borderserver using said first protocol via said first network; wherein saidprocessor controls a fourth component that translates said data fromsaid first protocol to said second protocol; wherein the processorcontrols a fifth component that communicates said data said between aserver at the network operations center and said destination device insaid second protocol using said second network operating under saidsecond protocol; wherein said processor controls a sixth component thatmaintains a third connection between said originating device and asecond border server at said network operations center using a thirdnetwork operating under a third protocol; and wherein said processorcontrols a seventh component that, when said first connection fails,communicates said data between said destination device and said secondborder server using said third protocol via said third network, whereinsaid processor controls said plurality of components based uponinformation retrieved from said memory; wherein said first connectionfails when a capacity of said first connection decreases below athreshold, and wherein a capacity of said data over said failed firstconnection is above the threshold.
 16. The system of claim 15, furthercomprising: a data encapsulating component at said originating deviceconfigured to encapsulate said data communicated from said originatingdevice, wherein said encapsulated data is communicable using said firstprotocol and said third protocol.
 17. The system of claim 16, whereinsaid data encapsulating component is a network protocol layer.